Peter Knight

Just implemented a similar concept in my own changelog. https://www.peterknight.digital/docs/mediahub/v1/changelog/

Snap @Kiwi Chris. I view these often too. Here’s the Plesk colour coded change log.

Thanks @HMCB 🙂

Good morning everyone * MediaHub had an update to 1.21.1 and a few quiet releases in between. File Types The sidebar gains a new File Types filter. The file types only populate when a matching item exists. We already have a Types filter on top of your Library, but this is more granular, and I find myself using it much more than its addition suggests. Utilities Someone suggested it'd be useful to see their unused assets real quickly. While I was adding this, I introduced some other useful filters. Here's the full set… Image variations The asset detail page gets an additional image variations table. If you've worked with PW for a while, you know how these can build up, so having visibility on them can illustrate that volume. Upload queue Another good user suggestion. Whan an upload is complete, they wanted a quick way to jump to that asset or back to the Library. Combo fields (fixed) Removing an asset from a MediaHub picker inside a Combo field wasn’t working. Fixed now. Title and alt on field upload. If you upload into a MediaHub field and type a title or alt in the sidebar before you save the page, those values now go onto the library record. Other uses of the same asset inherit them. Promoting custom fields the same way is still on the list. Download MediaHub 1.21.1 is available from your downloads area. Thanks everyone. I didn't @ peoples names in this post, but you'll recognise your suggestions. P * It was actually morning when I started writing this.

Yes, same here. This is getting ridiculous. I had to do some actual work today and couldn't use the forums for general procrastination😉

When I needed to build a store for my module, I did a few laps of the various payment providers. I wanted license distribution, payment integration and processing, Merchant of Record and tax compliance, user registration and login, and for users to be able to login to their account, view their downloads, manage subscriptions etc. Basically everything the Pro modules encompass but obviously, I couldn’t ask that the product was integrated with the forums. So, honestly, I just asked AI to help me build everything I need. I think it’s important we “eat our own dogfood” so having it run on ProcessWire was the optimal situation for me. PromptWire built the whole system in a few hours. The fields, templates, everything. The only thing I changed was to adopt Ryan’s Login Register Pro to retire my initial registration DIY setup etc. If it’s any help, I can share any and every detail of this but perhaps somewhere else. My point (finally) is that this can be done with PW itself as the engine. Briefly, I chose Paddle for payment processing as it handles international VAT compliance. My issued licenses are automatically generated by PW and emailed upon a sale. I recently discovered that Stripe has launched their MoR service. It has higher fees but is more powerful than some other solutions. I might even switch but I have a soft spot for Paddle due to its simple setup. For a module store such as Craft etc I believe Stripe Connect is used. This is the sub product which automatically pays the module creators when there’s a sale On the topic of hosting other modules ZIPs and issuing licenses, I am not sure how this is extended to 3rd party modules. So I suspect a reasonable direction to start with is that module creators can have a profile or a module page with X screenshots and initially, people are simply directed to the creators site which will handle sales, marketing, docs etc. Modules listed on the official PW modules store might even pay a small fee to be listed? Just a brain dump but I don’t think we need to boil the ocean here. Let’s start small and figure it out as we go. Currently there are only a handful of commercial modules anyway, so it’s a good time to move slowly and we can afford a little experimentation? P Ps attached is an outline of how other CMS platforms handle their module stores. According to Claude. marketplace-payment-delivery-licensing-outline.pdf

I may be overlooking an existing limitation or requirement, but it seems to me there's no reason the forum software has to (or even should) support a commerce function. IMHO, software for sale should live on the ProcessWire site and should not be bolted onto a forum ?

Yep, every day 😕 It's quite random too. Is it filtering by IP or location?

Quick follow-up, AKA "marketing and sales" chores I'm not supposed to ignore. Use the discount code mediahub11201 at checkout. First 3 licenses only, until Sunday night. BTW, we also support PPP pricing, so if that pricing is still a stretch in your part of the world, pop me a message. Cheers P

I’d settle for simply getting these forum 403 errors fixed 😜

@joaomota just curious, but did you ever get this fixed?

Happy Wednesday, everyone! Does such a thing exist? Such a question is beyond this post's remit. So let me introduce you to MediaHub 1.20.0 to 1.20.1 instead, which features: Field automation (pre-generated sizes, collection filing, labelling) findRaw() variations SVG display in the library Library and picker polish Integrator hooks We're going without screenshots today, since most changes aren't visual. Field automation A collection of field automations that shortens the resize–file–label round-trip after every upload. Pre-generated size variations. Give a field a list of sizes, MediaHub will generate those variations up front on upload and save. The first visitor gets a cache-hot image instead of triggering GD on demand. These are ordinary ProcessWire variations on disk, not separate library items: they do not appear in the grid and do not inflate your asset count. A per-request limit keeps large galleries from hitting PHP's execution-time cap. Automatic collection filing. Point a field at a collection path, static (e.g. /news/images/) or built from the page's own fields (e.g. /news/{title}/{date:Y-m}/), and its assets are automatically filed into that collection when the page saves. Missing collections are created automatically. Automatic labelling. Same idea for library labels: a static list, or labels built from page fields (e.g. {category.title}). Labels are applied on save; empty placeholders are skipped. Slow-save overlay. When automation makes a save take a moment, a brief loading overlay appears in the page editor so it does not look broken. Thanks to @David Karich of Flipzoom for the automation concepts, code samples and testing. Full setup steps and more examples are in the new Field automation documentation. findRaw() variations (1.20.0) findRaw() now accepts an opt-in variations field: name, URL, dimensions, filesize for size variations already on disk. These are read-only and pair with pre-generated sizes for cache-hot galleries without lazy resize on first visit. Docs: findRaw SVG display in the library SVG support arrived in 1.17, but transparent SVGs were still hard to work with in the library. White or light artwork could disappear against the tile background, and the artboard edge was unclear. 1.19.52 treats transparent SVGs properly across grid, list, masonry, and asset detail views: a dot-grid preview behind the artwork, a subtle frame with drop shadow and corner radius, and masonry that no longer upscales icons and logos beyond their intrinsic size (photos still fill the column width). If your library holds brand marks or UI icons as SVG, browsing them should feel much closer to working with raster thumbnails. Thanks to @Stefanowitsch for flagging this. Library and picker polish Bulk delete with usage awareness. Selecting multiple assets and deleting them used to show a generic confirmation even when some were still referenced on pages. The dialog now checks all selected assets in a single pass (one query per field, not one per asset). When any are in use, the message leads with how many are used on pages, matching the tone of the single-asset warning, and the confirm button reads Delete Anyway. Picker sidebar resize. The main library sidebar gained resize in 1.19.51, but the picker modal's handle was visible without doing anything. 1.19.52 fixes drag-to-resize in the picker and remembers the picker's width separately from the main library. Template picker hygiene. MediaHub's internal templates no longer appear in ProcessWire's "Add New Page" template picker at arbitrary tree locations. They are hidden from editors and tagged for clearer grouping under Setup → Templates. Thanks @Didier B. There's a ton of other stuff in 1.20.X spanning a few releases. The Changelog is up to date and a good place to see everything across the releases. Thanks for reading Peter

Slack might be more versatile, but I imagine not everyone has Slack. Maybe it's more important to get started, and a private forum is a good and quick starting point? Open to ideas. Regarding the Sponsorship stuff, I'll pop you a DM.

Hey @ryan This is music to many users' ears, I imagine. I think we've all felt that ProcessWire was suffering from a lack of exposure and marketing. Many of us are ready for lift-off and PW has never been stronger. Every time I open my social channels, I see people abandoning WordPress, but those people are not necessarily finding ProcessWire. More on this later. I'd like to hold up my hand for strategies and ideas around marketing, SEO and social media help. Implementation too, obviously. identifying topic-clusters we can create content on to capture "WordPress alternative" searches and the myriad of CMS related queries. The whole SEO Hub and Spoke approach. Creating those blog posts not only on my own website but versions for the ProcessWire website Community oriented social posting - IE organising social posts we could ask people to publish Identifying website content gaps beyond technical readers I've helped a few clients in exceptionally tough and competitive industries get cited in AI and achieve high 'traditional' rankings too with variations of the above. I know there are many people here with many overlapping skills. We all have various amounts of time and commitment. We just need a shared collaborative space where we can get started. I'd suggest not using the forums as they can be indexed. Regarding item 2 Processwire is a fundamental part of my working life and has enabled us to make a living, make profits and pay the bills. Lots of us support PW via Pro modules both when we need them and occasionally renew to keep the project going. If you're not changing from Open Source to a small per-site license, I think there are a variety of opt-in avenues people might be amenable to that both keep the project open source and allow people to contribute back to the project. A sponsorship - Gold, Silver, Bronze A yearly 'Friends of' type voluntary contribution A small annual subscription for PRO modules. Maybe the entire bundle, as you mention A dedicated PRO support plan Just lobbing these out there for consideration. And my motivation is not simply because I have some of my own Modules. I've felt this way for years.

I realise this post is a few years old but I just visited your site. Lovely work. It's clean, well designed (obviously) and easy to navigate. Some lovely animation too. You never proceeded with the English translation? P